Skip to content

gpt-luna-5.6 is different in opencode go req fix gpt luna unuse - #8

Merged
Abbalochdev merged 2 commits into
Abbalochdev:mainfrom
wylasdasd:main
Aug 28, 2026
Merged

gpt-luna-5.6 is different in opencode go req fix gpt luna unuse#8
Abbalochdev merged 2 commits into
Abbalochdev:mainfrom
wylasdasd:main

Conversation

@wylasdasd

@wylasdasd wylasdasd commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

部分支持。 大部分 Go 模型能用，但 gpt-5.6-luna 这类走 /responses 的模型，主聊天链路还不支持。

已支持
主客户端 GLMClient 只实现了两种协议：

协议 实际请求地址 适用模型
OpenAI
…/chat/completions
GLM、Kimi、DeepSeek、MiMo、Hy3 等
Anthropic
…/v1/messages
MiniMax、Qwen、Claude

core.ts
Ln 70–71

  • Supports both OpenAI-compatible (/chat/completions) and
  • Anthropic-compatible (/v1/messages) protocols. OpenCode Go 上这两类模型在 Copilot Chat 里都能正常用。

还不支持（Luna 的问题）
gpt-5.6-luna、grok-4.6、muse-spark-1.2-contributor 在 OpenCode Go 文档 里走的是 /v1/responses，不是 /chat/completions。

插件会把 Luna 当成普通 OpenAI 模型，路由到 opencode-go

@wylasdasd
gpt-luna-5.6 is different in opencode go req fix
960a767 
部分支持。 大部分 Go 模型能用，但 gpt-5.6-luna 这类走 /responses 的模型，主聊天链路还不支持。

已支持
主客户端 GLMClient 只实现了两种协议：

协议	实际请求地址	适用模型
OpenAI
…/chat/completions
GLM、Kimi、DeepSeek、MiMo、Hy3 等
Anthropic
…/v1/messages
MiniMax、Qwen、Claude

core.ts
Ln 70–71
* Supports both OpenAI-compatible (`/chat/completions`) and
* Anthropic-compatible (`/v1/messages`) protocols.
OpenCode Go 上这两类模型在 Copilot Chat 里都能正常用。

还不支持（Luna 的问题）
gpt-5.6-luna、grok-4.6、muse-spark-1.2-contributor 在 OpenCode Go 文档 里走的是 /v1/responses，不是 /chat/completions。

插件会把 Luna 当成普通 OpenAI 模型，路由到 opencode-go
@wylasdasd

wylasdasd commented Aug 27, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

old
image

fixed

image

GPT-5.6 Luna, Grok-4.6, and Muse Spark 1.2 Contributor use /v1/responses in the OpenCode Go documentation, not /chat/completions.

@wylasdasd wylasdasd closed this Aug 27, 2026
@wylasdasd
fix bug
fc6c6e8 
fix(vision): use getApiKey after unified auth removed getApiKeyForEndpoint
Auth was consolidated to a single Go/Zen API key, but automatic vision
still called authManager.getApiKeyForEndpoint(), causing image requests
to fail with "getApiKeyForEndpoint is not a function".
@wylasdasd wylasdasd reopened this Aug 27, 2026
@wylasdasd

wylasdasd commented Aug 27, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

second commit fix bug
image

fixed
image

fix(vision): use getApiKey after unified auth removed getApiKeyForEndpoint
Auth was consolidated to a single Go/Zen API key, but automatic vision
still called authManager.getApiKeyForEndpoint(), causing image requests
to fail with "getApiKeyForEndpoint is not a function".(it is I delete go and zen selectitembox caused )

@Abbalochdev
Abbalochdev merged commit 2a10669 into Abbalochdev:main Aug 28, 2026
0 of 2 checks passed
Abbalochdev added a commit that referenced this pull request Aug 28, 2026
@Abbalochdev
chore: release v3.11.15 (PR #8) + document PR #7 (v3.11.14)
a8c84bd
@Abbalochdev

Abbalochdev commented Aug 28, 2026

Copy link
Copy Markdown
Owner

Hello, could we revalidate the Swarn Agents structure flow to make it flawless and efficient in parallel usage with more advanced capabilities to run multiple agents individually to complete a single task more accurately and efficiently in a shorter amount of time?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@wylasdasd @Abbalochdev